home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
tsql
/
doc
/
tsql.mail
/
000148_edrbtsn@cs.indiana.edu _Mon Jun 7 13:27:01 1993.msg
< prev
next >
Wrap
Text File
|
1996-01-31
|
1KB
|
32 lines
Message-Id: <199306071827.AA12309@optima.CS.Arizona.EDU>
Received: from bigeye.cs.indiana.edu by optima.CS.Arizona.EDU (5.65c/15) via SMTP
id AA12309; Mon, 7 Jun 1993 11:27:07 MST
Received: by bigeye.cs.indiana.edu
(5.65c/9.4jsm) id AA06330; Mon, 7 Jun 1993 13:27:03 -0500
From: "Ed Robertson" <edrbtsn@cs.indiana.edu>
Subject: are queries easy to write?
To: tsql@cs.arizona.edu (TSQL working group)
Date: Mon, 7 Jun 1993 13:27:01 -0500 (EST)
X-Mailer: ELM [version 2.4 PL21]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 827
| Rick Snodgrass says:
|
|1. .... Five queries can't be that hard to write.
In fact, for some categories it is difficult to come up with NATURAL
queries which aren't variations on the same theme. For instance,
there are few occasions where one is interested only in the time of
some facts (class O2 - boy this may get me in trouble: "O2 doesn't
make sense sometimes" :-). The exceptions are very local queries,
when we already know the fact and just wish its time, or very global
queries, concerning the overall state ("when were there the most
employees") which require aggregation or forall.
Anyway, maybe we should have some indication when certain categories
seem less natural. This would facilitate purning out classes. How
about a macro like \classremark#1 which Christian can define as he
pleases, including null.